SUPPORT / SAMPLES & SAS NOTES
Problem Note 61116: After you upgrade from SAS® Infrastructure for Risk Management 3.3 to 3.4, subflows are read from the wrong federated area
 |  |  |  |  |
If you upgrade from SAS Infrastructure for Risk Management 3.3 to 3.4 and then modify a subflow for the 3.4 release that exists in the federated areas in both releases, the subflow for the 3.4 release is read from the 3.3 federated area. When this issue occurs, errors like the following are generated in the server log.
ERROR: Metadata Server denied access to operation.
ERROR: Write access to member VALIBLA.NEW_TABLE.DATA is denied.
ERROR: Unable to connect to Metadata Server.
ERROR: Execution terminated by an ABORT CANCEL statement
ERROR: Write access to member VALIBLA.NEW_TABLE.DATA is denied.
ERROR: Unable to connect to Metadata Server.
ERROR: Execution terminated by an ABORT CANCEL statement
ERROR JobFlowExecutor:974 - JobFlowExecutor: The execution of Task UpToLasr(key: 1966144076) failed with exception com.sas.solutions.risk.irm.server.task.MvaTaskLogErrorException: The task ID="_3" ("UpToLasr") had 4 errors in the execution log (return code was {3}).
com.sas.solutions.risk.irm.server.task.MvaTaskLogErrorException: The task ID="_3" ("UpToLasr") had 4 errors in the execution log (return code was {3}).
at com.sas.solutions.risk.irm.server.taskexec.SASHelper.checkLogForErrors(SASHelper.java:2441)
at com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable.executeAllAndGetResults(MvaTaskRunnable.java:896)
at com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable.run_local(MvaTaskRunnable.java:591)
at com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable.run(MvaTaskRunnable.java:394)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at java.lang.Thread.run(Thread.java:745)
com.sas.solutions.risk.irm.server.task.MvaTaskLogErrorException: The task ID="_3" ("UpToLasr") had 4 errors in the execution log (return code was {3}).
at com.sas.solutions.risk.irm.server.taskexec.SASHelper.checkLogForErrors(SASHelper.java:2441)
at com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable.executeAllAndGetResults(MvaTaskRunnable.java:896)
at com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable.run_local(MvaTaskRunnable.java:591)
at com.sas.solutions.risk.irm.server.taskexec.MvaTaskRunnable.run(MvaTaskRunnable.java:394)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at java.lang.Thread.run(Thread.java:745)
There is no workaround.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Infrastructure for Risk Management | Microsoft® Windows® for x64 | 3.4 | 3.5 | 9.4 TS1M5 | 9.4 TS1M5 |
| Linux for x64 | 3.4 | 3.5 | 9.4 TS1M5 | 9.4 TS1M5 | ||